home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 3: CDPD 3
/
Almathera Ten on Ten - Disc 3: CDPD3.iso
/
scope
/
051-075
/
scopedisk72
/
tag-25
/
tag_libraries
< prev
next >
Wrap
Text File
|
1995-03-19
|
12KB
|
253 lines
read-first... libraries for the tag bbs system are a very
efficient entity. they should be set-up with the following
policy... if you support only one computer.. such as amiga..
you should only have one library and all files should be
in it. this is for a number of reasons that will become
apparrent to you later. if you have support for amiga,ibm,
attari and c64... in the same vein, you should have 4
libraries.
the comments, including this line can be deleted when you
put this and the other necessary files into the 's'
directory if your disk space is critical. they are there
only to help you fill in the entries in the parameters.
the tag-parser only looks for the keywords, in upper-case
followed immediatly by a colon and then followed by
parameterizing data.
the following group of 5 lines should be duplicated exactly
as presented in the first group of 5 lines as many times as
necessary to describe your libraries. the second set of 5
lines are provided only for your use to copy as many times
as you feel necessary!
******** n o t i c e **************
* each library must exist in its *
* own unique and separate *
* disk directory!!! *
***********************************
LIBRARY: Amiga-files
LOCAT: c2:bbs/AmigaFiles/
UPLOAD: 1,255
DOWNLOAD: 2,255
FILES: 1800
LIBRARY:
LOCAT:
UPLOAD: 1,255
DOWNLOAD: 255,255
FILES:
the folowing 'nlibs' should contain the decimal number of
libraries you have!! this is the over-riding parameter
that determines just how many libraries you will generate
(or post generate.. the number of libraries you will activate
at startup time) on your system.
NLIBS:1
the following paramater 'libpolicy' tells the program about
compensation for file uploads. note: free upload will give
back time even for failed uploads but NO premium time
unless the upload WAS successful!
-1 = no compensation
0 = free uploading
+n = free uploading + (premium mins)
premium mins = (#K of upload)*(n)
(note:libpolicy is floating point)
(suggest: n=.30) this will give an extra 12 minutes for
a successful 40k upload!
LIBPOLICY:0.215
the folowing parameter 'ncats' equals the decimal number of
sub-file titles.
note, also, this number must be ODD!! this is because
the catagories are listed to your users in 2 columns
and an even number will make the columns uneven.
NCATS:29
the following group is the list of catagories for the
sub-file titles on ALL of the libraries. no provision
is made to allow different sub-file catagories for
different libraries. note..the numbers BEFORE the
capitol 'v' is to help keep count on the number of
sub-file catagories (for notation only)! the parser
in the generate utility only looks for a capitol 'v'
followed imediately by a 'colon'. also, there is no
separate security for each of the sub-catagories. if
you want security... create another library and set
its security separately!! see 'subprot below'!!
1V:ALL
2V:General
3V:Utilities
4V:Games
5V:Communications
6V:Icons+Fonts+Ptrs
7V:Sound
8V:Pictures
9V:Videos
10V:C tools+source
11V:Wedges
12V:Word Processing
13V:Accounting
14V:C.A.D.
15V:Data Base Manager
16V:**ADULT**
17V:Backups
18V:INFO-TEXT files
19V:Virus Stuff
20V:ARP stuff
21V:C.A.B. stuff
22V:Hacks
23V:Demos
24V:Disk Utilities
25V:Educational Stuff
26V:Diagnostics
27V:Astronomy
28V:Other Languages
29V:Fish+Amicus Disks
a protection mode is provided to keep certain eyes
out of certain files.
if this mode is used... the sub-lib #'s contents
(in all libraries of your bbs) will not appear to
a user with less than a '3' access level. this is
hard coded in tag!
as an alternative; you always can turn
this off (see below) and just set the security on an
entire library to an access 3.. that will also work
and will lock out that library and all sub-libs in
that library. this can be used for more purposes
than censorship if, on your board, censorship is not
an issue. perhaps contributing members get this
access. its yours as sysop to use as you see fit.
power and flexibility is the result!
the mechanism works like this.. the parameter
following 'subprot:' (in caps) refers to the
sub-lib above that will be marked protected to
anyone who's access is < 3. this, in essance, is
making another security level just above the
'valid' level. But more than that... catalog and
list will not even show the file's existance! when
you put a file in this sub-lib.. you should set
that file's security to 3 also!!
if you wish to not use this security avenue, simply
set this parameter to a number higher than the
highest sub-lib in existance on your board (9999)!
please note: the number of the file matches the
position in the list above.. not the actual sub-dir
number.. as are all... offset by one!
SUBPROT:16
the following 2 params denote if you have arc and/or
zoo available on your c: directory and want to allow
your users to 'view' library files. if, for some reason
you want to turn one or the other or both of these off
simply put zero ('0') after the one(s) you want to
disable! Wasn't going to allow switching this parameter
but some are running off of floppies and arc and zoo
take up 100K of disk space.
the parameter 'workpath' is where the arc and zoo are
to do thier work. the file you want to view.. will be
copied here (a root directory or an empty sub-directory)
and manipulated by arc or zoo and then deleted!! this
was done for users with more disk space than ram space.
if you have a decent sized ram-disk.. continue to use
ram: .like all the other path determining strings..
be sure this ends with either a slash(/) or a colon(:)!
ARCYES:1
ZOOYES:1
WORKPATH: c2:bbs/t/
The following parameter allows you to limit the
file-types you are going to allow on your board.
personally, i feel that only '.arc', '.zoo' and '.pak'
files should be uploaded to my board.. as storage
of raw files take up too much space on my file disk
and the transfer of un-acrhived files puts them at
risk.. due to x-modem not auto-chopping the data it
puts into the file!
remember.. as sysop... there is NO limitation of any
kind placed on what you upload.
if you do not want any controls on uploads from
your users... put '0' in this parameter and your users
will be permitted to upload any types of files to your
board. there is a maximum number of parameters allowed.
this maximum is presently = 15 and their length can
only be up to 6 characters each(counting the manditory
'*.'). note that there is no case sensitivity.. upper
and lower case have the same effect.
immediatly after should be the familliar
(capitol) 'v:' then followed by the '.arc' or whatever.
see the examples below.
POSTCONTROLS:5
V:*.arc
V:*.zoo
V:*.pak
V:*.wrp
V:*.txt
the following parameter is for dn/upload monitoring.
this is the 'main' switch to cause your
board to monitor your upload/download ratio from your
users..... '0.0'=disable!! Anything greater will be the
base BASE upload/download ratio!! NOTE.. this is a
FLOATING-POINT variable!!
a file named 'leech-log' is sent to your tag's
system directory and appended with each leech or
near-leach download attempt.
you, as sysop, can lower the daily time allotment
to force the offending user to upload in order to
gain enough time to download. The 10.0 below suggests
that a 10:1 ratio is acceptable on this board.
LEECH_CHECK:3.0
the folowing params following the 'k:'s specify the
switching points for your users catagories.
'(leech_check * (uploads + 1)) (minus) downloads'. the catagory is
described to the left of the 'k:' and is only
'comment'! this is the cataagory the user is informed
he is in.
1. execellent (>10:1) K:11.0
2. good/acceptable K:0.0
3. marginal/acceptble K:-0.2
4. failing.. totally!! K:-1.0
K: .. undefined ...expansion area
K:
anything between 3 and 4.. warns of doom.
anything < 4... tells the user that he is a
board-leech!!
both conditions (3 & 4) cause the user to acknowledge
receiving this message by inputting his
password once again. if he fails to do this
properly.. the download is aborted!
also.. both conditions also make a record
of this transaction and the user and how it
came out... are reported to the sysop in the
'leech-log'!!
the following parameter sets the maximum number of
actual files that a user can successfully download
from your board in any 12 hour period.
MAX_DL_PER_DAY: 5